Skip to content

Conversation

@prune998
Copy link

@prune998 prune998 commented Oct 6, 2020

Drone server is logging JSON by default.
This PR force the drone-runner-docker to log as JSON too.

@CLAassistant
Copy link

CLAassistant commented Oct 6, 2020

CLA assistant check
All committers have signed the CLA.

@tphoney
Copy link

tphoney commented Jul 20, 2021

Hey @prune998 thanks for the PR 🍺 !,
However this may have unforeseen implications of changing the output format, as people maybe relying on its current format. This is something that makes sense, would you change your PR to make this optional, so that it can be enabled by the end user if they choose.

@prune998
Copy link
Author

I'll look into this asap.

@prune998 prune998 force-pushed the prune/docker-runner-log-json branch from 16a979f to 89e7894 Compare July 20, 2021 20:40
@prune998
Copy link
Author

@tphoney I just added a bool flag to switch to json logs.
Please, review.

Thanks.

@bradrydzewski
Copy link
Collaborator

bradrydzewski commented Jul 21, 2021

The exec command is used to manually run build locally from an interactive terminate which is why we have text logging as opposed to json logging. Not sure we want json logging here. But it makes sense for the daemon.

Procs int64
Debug bool
Trace bool
LogJSON bool
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest backing out the changes to this file. The exec command is used for local development and testing only and we would never need / use json logging here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants